Posts tagged “agent feedback”

Four vibecoding terms, defined plainly: prompt, turn, context window, and agent-readable artifact. Each one changes how you write a review someone can act on.

A reusable prompt structure for handing Windsurf a cropped still, one numbered pin, and three tight bullets, so it edits the right element on the first turn.

Capture the broken screen, publish, then have Cursor read the whole review over MCP. The context for the fix is already in front of it before you type a prompt.

When you paste a feedback link into your coding agent, the image often falls away and the agent works from a URL it cannot see. Here is why that happens and how to hand it the actual screen instead.

An agent's chat summary vanishes when you close the tab. A captured, annotated review stays. Here is where each one fits and what each catches.

A five-step workflow for cropping the exact subcomponent, dictating a single change, and sharing a markdown link v0 can read.

Capture your Bolt preview, mark up what needs fixing, and hand Bolt a single markdown URL it can read. Here is the exact order of steps.

A short glossary for reviewers whose feedback ends up in an agent's context window. Define the artifact, the pin, the prompt, and what each one changes.

Agent feedback is not a vibe or a workflow buzzword. It is a specific artifact with a specific shape. Here is what it contains and why each piece is there.